Qameta Blog – QA Management

Shared context, shielded context: testers and developers writing tests together

This article discusses how developers and testers can collaborate on tests, despite having different approaches. Developers focus on code functionality, while testers prioritize readability and usability, but these differences can be addressed through automation and clear guidelines. Full-stack expertise for testers helps bridge these gaps, ensuring more effective and maintainable tests.

What our tests don't like about our code

Beyond just checking the correctness of our code, tests push us toward writing code that has less coupling and more cohesion. Let's explore the hints our tests give us with a simple weather script.

Reports create shared contexts for developers

Modern technical problems require T-shaped specialists who know how to communicate across team boundaries. So, how can you boost your communication APIs? Reports are an excellent tool for creating common context - encouraging people to talk to each other.

Quality Gates for Testers

Quality gates aren't just meetings with checklists - we believe automated tests make the best quality gates!

Legacy code and tests

Legacy is a word that we throw around often. Let's talk about how legacy appears, why we can't just shift the blame for it on someone else, and how automated tests can prevent your code from becoming legacy.

How to Enhance Productivity of TestOps Teams: Best Tips and Tricks

TestOps refers to the processes designed to manage the operational aspects of testing within SDLC. Let’s discuss how to enhance your TestOps team productivity.

QA as a process: where Shift Left and TestOps meet

Approaching QA as a process that has to be applied throughout the development cycle is a common topic for both Shift Left and TestOps. We've had a discussion with Parveen Khan, a proponent of Shift Left, and we hope you'll find it as interesting as we did!

Spreading TestOps through word of mouth

If you're already on board with TestOps, but your team isn't - what do you do? How do you convince the tester, the developer, the admin, and the product owner? And when is the right time to approach them? Read on to find out!

QA metrics for DevOps: the DORA keys

Since our last post about metrics, we've decided to take a look at some high-level indicators - and what better place to start than DORA? At the surface, those are just four (lately, five) numbers. But we'd like to show you that they are not as straightforward as they might seem, and there's a lot of stuff happening under the hood.

QA metrics for DevOps: how to make them work

Playing with numbers is fun, but collecting metrics can be a complicated process that will take up your time and energy. Here, we'll take a look at some of the potential pitfalls on the road to building a meaningful metric.

Code coverage as a target

Calculating code coverage is a relatively simple way of checking how well your test suite is written. But how useful is this metric? Let's find out!

Automated requirement coverage calculation and its visualization in Allure Framework

Do you want to know how to turn the requirement coverage metric into an actual linter for your codebase? Read more to find out! This is a case study about an automated pipeline with that metric.

Defect Management Process

Defects are destructive at any software development stage.However, defects are present in all software because _humans create software_ — which means inevitable human error during production.